JBoss Community Archive (Read Only)

Mobicents

XML Format

For the SNMP adaptor, the attributes.xml consists of three types of elements: the top-level <attribute-mappings>, <mbean> and <attribute>. The <attribute-mappings> tag contains a list of <mbean>s. Each <mbean> tag must have a name attribute that indicates the JMX ObjectName of the MBean to monitor. The <mbean> also contains a list of <attribute> tags. Each <attribute> tag requires a name, which corresponds to an MBean attribute name, and an OID, which indicates what OID this particular <attribute> can be queried at. The rest of these instructions assume a basic understanding of the SNMP adaptor attributes.xml format.

In addition to the standard elements and attributes that the SNMP adaptor uses in its attributes.xml, the MIB generator can make use of several additional attributes, a few of which are required for a valid MIB to be generated. The optional attributes will not interfere with the SNMP adaptor, and so the same file can be used for both purposes. There are two elements of importance in the attributes.xml that have received the changes, and we will go into them in detail here. Within this explanation, <mbean> means the element defined within the attributes.xml, <attribute> means any element defined within an <mbean>. MBean refers to the actual MBean on the server, and attribute (without tags) refers to the XML meaning.

attribute Element

The <attribute> is defined like this: <attribute name="distributable" oid=".2"/>

This element denotes an Object or Metric contained in the <mbean> this <attribute> was defined in. The valid attributes are listed below:

Name

Purpose

Importance

Default Value

name

The name of the metric on the MBean. Must match exactly to such a metric.

Required

Not applicable

oid

The numeric identifier SNMP uses to identify this particular attribute. Can be a single number, or a full OID, if the <mbean> doesn't define a prefix.

Required

Not applicable

mode

Indicates whether this MBean attribute should be writeable via SNMP.

Optional

ro (read only)

snmp-type

MIB Generator specific. The type SNMP managers should attempt to interpret this attribute as.

Optional

OCTET STRING (SIZE (0..255))

max-access

MIB Generator specific. Set the type of access SNMP managers should have to this attribute.

Optional

read-only

description

MIB Generator specific. A description of the attribute that will be place in the MIB.

Optional

""

status

MIB Generator specific. The SNMP STATUS of this attribute.

Optional

current

table

MIB Generator specific. Indicates that this attribute should be treated as a table. Suitable for MBean metrics that are Arrays, Lists, or Maps, if direct access to elements is desired.

Optional

false

Each <attribute> will have its own MIB definition. What is contained in this definition depends on the attributes defined in the <mbean>, and the amount of optional attributes defined in the <attribute> itself. Here's an example MIB Object, with placeholders for each attribute in the <attribute>. 

<name> OBJECT-TYPE
        SYNTAX <snmp-type>
        ACCESS <max-access>
        STATUS <status>
        DESCRIPTION
                "<description>"
::= { <definition-name> <oid> }

The definition-name attribute comes from the <mbean>, as will be seen later. All of the optional attributes are to help the MIB be more complete; they are not strictly required for a valid MIB to be produced. The <attribute> element is rather simple, as is the transformation from the XML into MIB form. It is necessary to understand the purpose of these optional attributes before moving on to the more complicated part, the <mbean> element.

mbean Element

The <mbean> is defined like this:  <mbean name="jboss.system:type=ServerInfo" oid-prefix=".1.3.6.1.4.1.2312.100.1.1" definition-name="jbossAsObjects">

This element denotes an MBean which you would like to monitor with SNMP. The valid attributes are listed below:

Name

Purpose

Importance

Default Value

name

The name of the mbean to be monitored by the snmp-adaptor. Can be a pattern / wildcard. Must be in ObjectName form.

Required

Not applicable

oid-prefix

The value contained in this attribute will be prepended onto all of the <attribute> elements contained in this <mbean> element.

Optional

""

definition-name

The name to give the value contained in the oid-prefix field in the MIB, if any.

Required1

Not applicable

table-name

Table specific. The name for the entry in the MIB if name is a wildcard.

Special2

"UNKNOWN"

description

Table specific. The description about this <mbean> that will be placed into the MIB, if it is a table.

Optional

""

status

Table specific. The SNMP status of this object.

Optional

"current"

1: This attribute must be defined if there is an oid-prefix defined, and no other <mbean> element with the same oid-prefix defines a definition-name, for correct MIB generation.

2: This attribute must be defined if the name of the <mbean> is a pattern / wildcard.

Example of a standard <mbean> definition, within a minimal attributes.xml: 

<attribute-mappings>
 <mbean name="jboss.system:type=ServerInfo" oid-prefix=".1.3.6.1.4.1.2312.100.1.1">    
    <attribute name="ActiveThreadCount" oid=".1"/>
 </mbean>
</attribute-mappings>

Each <mbean> element contains within it any amount of <attribute> elements. These <attribute> give the name of the MBean attribute you want to monitor, as well as assign an OID to that attribute.
With the oid-prefix defined, each <attribute> will have this value prepended to it. So, ActiveThreadCount's effective OID is: 1.3.6.1.4.1.2312.100.1.1.1.0 because this is not a table, thus all <attributes> are treated as scalar SNMP values. The above <mbean> definition is good enough for the snmp-adaptor. However, there is not enough information in this <mbean> for a proper MIB entry to be generated. This is where the additional attributes for <mbean> come in. If we use the generator (downloadable from https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/mibgen-generator/1.0/mibgen-generator-1.0-executable.jar) on the above attributes.xml, we will get the following: 

[thauser@tommycat mibs]$ java -jar mibgen-generator-1.0-executable.jar -a attributes.xml -m TEST-MODULE -o TEST.mib
There was no definition-name for oid-prefix: 1.3.6.1.4.1.2312.100.1.1

This is because there is no other <mbean> with a definition-name for that oid-prefix. Only one <mbean> needs a definition-name attribute defined if they have the same value in their oid-prefix attribute. The definition-name must be defined in the first <mbean> that uses a specific oid-prefix. Any subsequent definition-name attributes which are associated with the same oid-prefix will be ignored. As an example: 

<attribute-mappings>
 <mbean name="jboss.system:type=ServerInfo" oid-prefix=".1.3.6.1.4.1.2312.100.1.1" definition-name="definition1">    
    <attribute name="ActiveThreadCount" oid=".1"/>
 </mbean>
 <mbean name="jboss.system:type=AnotherMbean" oid-prefix=".1.3.6.1.4.1.2312.100.1.1" definition-name="definition2">
    <attribute name="AnotherAttribute" oid=".1"/>
 </mbean>
</attribute-mappings>

In this case, the MIB will associate the name "definition1" with 1.3.6.1.4.1.2312.100.1.1 in the MIB, and will ignore the "definition2" in the 2nd <mbean>, because it has the same value in its oid-prefix attribute.
If the first <mbean> had no definition-name defined, the same error as above would be thrown, even though "definition2" is defined.

Here is the MIB generated using the above command, with the above example attributes.xml: 

-- This MIB Generated by the JBoss MIB Generator

TEST-MODULE DEFINITIONS ::=BEGIN

IMPORTS
    OBJECT-TYPE,
    NOTIFICATION-TYPE,
    Counter32,
    Gauge32,
    Counter64,
    TimeTicks
        FROM SNMPv2-SMI
    DisplayString,
    TruthValue
        FROM SNMPv2-TC;

definition1        OBJECT IDENTIFIER ::= { 1 3 6 1 4 1 2312 100 1 1 }

activeThreadCount OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { definition1 1 }

anotherAttribute OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { definition1 1 }

END

The definition-name is the only required attribute for MIB generation to complete correctly. The other attributes are there to make the resulting MIB more exact and verbose, with the exception of the table-name attribute. This attribute has a special role, for use when the given <mbean> name is a wildcard. 

Example of a wildcard <mbean> definition: 

<mbean name="jboss.web:host=localhost,path=*,type=Manager" oid-prefix="1.3.6.1.4.1.2312.100.1.1.30.1" definition-name="testTableDef" table-name="test" status="current">
      <attribute name="distributable" oid=".2" snmp-type="INTEGER"/>
      <attribute name="sessionCounter" oid=".3" snmp-type="INTEGER"/>
      <attribute name="activeSessions" oid=".4" snmp-type="INTEGER"/>
</mbean>

Since the name attribute in this definition is a wildcard, it may match more than one MBean on the MBeanServer. The snmp-adaptor will put all values into a table, which is indexed by the ObjectName returned by a query into the MBean server on the given wildcard. In the MIB, this MBean definition will be split into three entries; one defining the table itself, one defining a table row, and one defining the SYNTAX of the table row. The way these are defined is dependent on the definition-name, table-name, and oid-prefix attributes. The list of <attribute> will be added to the MIB below these three entries, and their OIDs will be prefixed with the full value of the oid-prefix attribute.

An example of the three entries, with placeholders for relevant fields:

The oid-prefix is chopped up in order to have oids that make sense for every one of these entries. More detail below.

The Table entry: 

<table-name>Table OBJECT-TYPE
    SYNTAX    SEQUENCE OF <table-name (Capitalized)>Entry
    MAX-ACCESS    not-accessible
    STATUS    <status>
    DESCRIPTION
        "<description>"
::= { <definition-name> <2nd to last number in oid-prefix> }

Note: This second to last number in oid-prefix must not clash with another object in the MIB, if the rest of the oid-prefix is not unique.

The Row entry: 

<table-name>Entry OBJECT-TYPE
    SYNTAX    <table-name (Capitalized)>Entry
    MAX-ACCESS    not-accessible
    STATUS    current
    DESCRIPTION
        "<description>"

        INDEX    {
        IMPLIED <table-name>ObjectName
        }
::= { <table-name>Table <last number in oid-prefix> }

Notice the capitalization differences in the attribute names in the next entry. This is done to make the MIB more readable, and to make sure there are no two tables with the same metric names.

The Syntax entry: 

 <table-name (Capitalized)>Entry ::= SEQUENCE {
    <table-name>ObjectName    DisplayString,
    <table-name>Distributable    INTEGER,
    <table-name>SessionCounter    INTEGER,
    <table-name>ActiveSessions    INTEGER
}

The interpretation of the oid-prefix is modified here. The oid of the Table MIB object is taken to be oid-prefix, except for the last number. The oid of the Entry MIB object is the full oid-prefix, and the attributes contained in the table function the same as in a normal <mbean>. However, the repercussions are that the definition-name will be matched up against the oid-prefix short the last two dotted numbers. If no definition-name exists for that OID, the same error encountered before will occur.

In this example, we have the following OIDs:

testTableDef = 1.3.6.1.4.1.2312.100.1.1
testTable = 1.3.6.1.4.1.2312.100.1.30 or testTableDef.30
testEntry = 1.3.6.1.4.1.2312.100.1.30.1 or testTable.1
testObjectName = 1.3.6.1.4.1.2312.100.1.30.1.1 (this is the index of the table) or testEntry.1
testDistributable = 1.3.6.1.4.1.2312.100.1.30.1.2 or testEntry.2
testSessionCounter = 1.3.6.1.4.1.2312.100.1.30.1.3 or testEntry.3
testActiveSessions = 1.3.6.1.4.1.2312.100.1.30.1.4 or testEntry.4

Below is the MIB entry that will be generated from the <mbean> above. 

testTableDef        OBJECT IDENTIFIER ::= { 1 3 6 1 4 1 2312 100 1 1 }

testTable OBJECT-TYPE
    SYNTAX    SEQUENCE OF TestEntry
    MAX-ACCESS    not-accessible
    STATUS    current
    DESCRIPTION
        ""
::= { testTableDef 30 }

testEntry OBJECT-TYPE
    SYNTAX    TestEntry
    MAX-ACCESS    not-accessible
    STATUS    current
    DESCRIPTION
        ""

        INDEX    {
        IMPLIED testObjectName
        }
::= { testTable 1 }

TestEntry ::= SEQUENCE {
    testObjectName    DisplayString,
    testDistributable    INTEGER,
    testSessionCounter    INTEGER,
    testActiveSessions    INTEGER
}

testObjectName OBJECT-TYPE
    SYNTAX DisplayString
    ACCESS not-accessible
    STATUS current
    DESCRIPTION
        ""
::= { testEntry 1 }

testDistributable OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { testEntry 2 }

testSessionCounter OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { testEntry 3 }

testActiveSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { testEntry 4 }

Note that the ObjectName object will always be present, as it is the index the snmp-adaptor uses in its internal representation. Thus, the user must not define any attribute with .1, or the MIB generation will fail.

As a final example, here is the Mobicents mss-attributes.xml, modified to allow MIB generation, and the resulting MIB:

Command used: 

java -jar mibgen-generator-1.0-executable.jar -a mss-attributes.xml -m TEST-MODULE -o TEST.mib
<?xml version="1.0"?>
<attribute-mappings>
   
   <!-- basic system information -->
   <mbean name="jboss.system:type=ServerInfo" oid-prefix=".1.3.6.1.4.1.2312.100.1" definition-name="jbossAsObjects">
      <attribute name="ActiveThreadCount" oid=".1"/>
      <attribute name="FreeMemory" oid=".2"/>
      <attribute name="MaxMemory" oid=".3"/>
   </mbean>

   <!-- tomcat global http request processing -->
   <!--<mbean name="jboss.web:name=http-0.0.0.0-8080,type=GlobalRequestProcessor">
      <attribute name="requestCount" oid=".1.2.3.4.1.5"/>
   </mbean>-->
   
   <!-- Tx Manager statistics -->
   <mbean name="jboss:service=TransactionManager">
      <attribute name="CommitCount" oid=".1.3.6.1.4.1.2312.100.1.6"/>
      <attribute name="RollbackCount" oid=".1.3.6.1.4.1.2312.100.1.7"/>
      <attribute name="TransactionCount" oid=".1.3.6.1.4.1.2312.100.1.8"/>
   </mbean>
   
   <!-- DefaultDS statistics -->
   <mbean name="jboss.jca:name=DefaultDS,service=ManagedConnectionPool" oid-prefix=".1.3.6.1.4.1.2312.100.1">
      <attribute name="InUseConnectionCount" oid=".9"/>
      <attribute name="MaxConnectionsInUseCount" oid=".10"/>
   </mbean>

   <!-- system information group see RFC-1213 -->
   <mbean name="jboss.jmx:name=SnmpAgent,service=MIB2SystemGroup" oid-prefix=".1.3.6.1.2.1.1" definition-name="system">
      <attribute name="SysDescr" oid=".1" mode="rw"/> <!-- can be modified over snmp -->
      <attribute name="SysObjectId" oid=".2"/>
      <attribute name="SysUpTime" oid=".3"/>
      <attribute name="SysContact" oid=".4"/>
      <attribute name="SysName" oid=".5"/>
      <attribute name="SysLocation" oid=".6"/>
      <attribute name="SysServices" oid=".7"/>
   </mbean>
   
   <!-- sip application dispatcher -->
   <mbean name="jboss.web:type=SipApplicationDispatcher" oid-prefix=".1.3.6.1.4.1.2312.100.1.11" definition-name="sipApplicationDispatcher">      
      <attribute name="baseTimerInterval" oid=".2" mode="rw"/>
      <attribute name="t2Interval" oid=".3" mode="rw"/>
      <attribute name="t4Interval" oid=".4" mode="rw"/>
      <attribute name="timerDInterval" oid=".5" mode="rw"/>
      <attribute name="memoryThreshold" oid=".6" mode="rw"/>
      <attribute name="backToNormalMemoryThreshold" oid=".7" mode="rw"/>
      <attribute name="gatherStatistics" oid=".8" mode="rw"/>
      <attribute name="requestsProcessed" oid=".9" />
      <attribute name="responsesProcessed" oid=".10" />
      <attribute name="congestionControlCheckingInterval" oid=".11" mode="rw"/>
   </mbean>
   
   <!-- sip stack -->
   <mbean name="org.mobicents.jain.sip:name=Mobicents-SIP-Servlets,type=sip-stack" oid-prefix=".1.3.6.1.4.1.2312.100.1.11.1" definition-name="mobicentsSipServlets">
      <attribute name="NumberOfClientTransactions" oid=".1"/>
      <attribute name="NumberOfServerTransactions" oid=".2"/>
      <attribute name="NumberOfDialogs" oid=".3"/>
      <attribute name="LocalMode" oid=".4"/>
   </mbean>
   
   <!-- Web Apps -->
   <mbean name="jboss.web:host=localhost,path=/*,type=Manager" oid-prefix=".1.3.6.1.4.1.2312.100.10.1" definition-name="sipManagerTableDef" table-name="manager">
      <attribute name="distributable" oid=".2" snmp-type="INTEGER"/>
      <attribute name="sessionCounter" oid=".3" snmp-type="INTEGER"/>
      <attribute name="activeSessions" oid=".4" snmp-type="INTEGER"/>
      <attribute name="maxActiveSessions" oid=".5" mode="rw" snmp-type="INTEGER"/>
      <attribute name="sessionAverageAliveTime" oid=".6" snmp-type="INTEGER"/>      
      <attribute name="expiredSessions" oid=".7" snmp-type="INTEGER"/>      
      <attribute name="rejectedSessions" oid=".8" snmp-type="INTEGER"/>
      <attribute name="maxInactiveInterval" oid=".9" snmp-type="INTEGER"/>
      <attribute name="sessionMaxAliveTime" oid=".10" snmp-type="INTEGER"/>                  
   </mbean>
   
   <!-- Sip or Converged Web+Sip Apps -->
   <mbean name="jboss.web:host=localhost,path=/*,type=SipManager" oid-prefix=".1.3.6.1.4.1.2312.100.11.1" definition-name="sipManagerTableDef" table-name="sipManager">
      <attribute name="distributable" oid=".2" snmp-type="INTEGER"/>
      <attribute name="sessionCounter" oid=".3" snmp-type="INTEGER"/>
      <attribute name="activeSessions" oid=".4" snmp-type="INTEGER"/>
      <attribute name="maxActiveSessions" oid=".5" mode="rw" snmp-type="INTEGER"/>
      <attribute name="sessionAverageAliveTime" oid=".6" snmp-type="INTEGER"/>      
      <attribute name="expiredSessions" oid=".7" snmp-type="INTEGER"/>      
      <attribute name="rejectedSessions" oid=".8" snmp-type="INTEGER"/>
      <attribute name="maxInactiveInterval" oid=".9" snmp-type="INTEGER"/>
      <attribute name="sessionMaxAliveTime" oid=".10" snmp-type="INTEGER"/>       
      <attribute name="sipSessionCounter" oid=".11" snmp-type="INTEGER"/>
      <attribute name="sipApplicationSessionCounter" oid=".12" snmp-type="INTEGER"/>
      <attribute name="activeSipSessions" oid=".13" snmp-type="INTEGER"/>
      <attribute name="activeSipApplicationSessions" oid=".14" snmp-type="INTEGER"/>
      <attribute name="expiredSipSessions" oid=".15" snmp-type="INTEGER"/>
      <attribute name="expiredSipApplicationSessions" oid=".16" snmp-type="INTEGER"/>
      <attribute name="rejectedSipSessions" oid=".17" snmp-type="INTEGER"/>
      <attribute name="rejectedSipApplicationSessions" oid=".18" snmp-type="INTEGER"/>
      <attribute name="maxActiveSipSessions" oid=".19" mode="rw" snmp-type="INTEGER"/>
      <attribute name="maxActiveSipApplicationSessions" oid=".20" mode="rw" snmp-type="INTEGER"/>
      <attribute name="sipSessionAverageAliveTime" oid=".21" snmp-type="INTEGER"/>      
      <attribute name="sipApplicationSessionAverageAliveTime" oid=".22" snmp-type="INTEGER"/>
      <attribute name="sipSessionMaxAliveTime" oid=".23" snmp-type="INTEGER"/>
      <attribute name="sipApplicationSessionMaxAliveTime" oid=".24" snmp-type="INTEGER"/>
      <attribute name="numberOfSipSessionCreationPerSecond" oid=".25" snmp-type="INTEGER"/>
      <attribute name="numberOfSipApplicationSessionCreationPerSecond" oid=".26" snmp-type="INTEGER"/>
   </mbean>
   
</attribute-mappings>
-- This MIB Generated by the JBoss MIB Generator

TEST-MODULE DEFINITIONS ::=BEGIN

IMPORTS
    OBJECT-TYPE,
    NOTIFICATION-TYPE,
    Counter32,
    Gauge32,
    Counter64,
    TimeTicks
        FROM SNMPv2-SMI
    DisplayString,
    TruthValue
        FROM SNMPv2-TC;

mobicentsSipServlets        OBJECT IDENTIFIER ::= { 1 3 6 1 4 1 2312 100 1 11 1 }
jbossAsObjects        OBJECT IDENTIFIER ::= { 1 3 6 1 4 1 2312 100 1 }
sipManagerTableDef        OBJECT IDENTIFIER ::= { 1 3 6 1 4 1 2312 100 }
sipApplicationDispatcher        OBJECT IDENTIFIER ::= { 1 3 6 1 4 1 2312 100 1 11 }
system        OBJECT IDENTIFIER ::= { 1 3 6 1 2 1 1 }

activeThreadCount OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { jbossAsObjects 1 }

freeMemory OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { jbossAsObjects 2 }

maxMemory OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { jbossAsObjects 3 }

commitCount OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { jbossAsObjects 6 }

rollbackCount OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { jbossAsObjects 7 }

transactionCount OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { jbossAsObjects 8 }

inUseConnectionCount OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { jbossAsObjects 9 }

maxConnectionsInUseCount OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { jbossAsObjects 10 }

sysDescr OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { system 1 }

sysObjectId OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { system 2 }

sysUpTime OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { system 3 }

sysContact OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { system 4 }

sysName OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { system 5 }

sysLocation OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { system 6 }

sysServices OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { system 7 }

baseTimerInterval OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { sipApplicationDispatcher 2 }

t2Interval OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { sipApplicationDispatcher 3 }

t4Interval OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { sipApplicationDispatcher 4 }

timerDInterval OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { sipApplicationDispatcher 5 }

memoryThreshold OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { sipApplicationDispatcher 6 }

backToNormalMemoryThreshold OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { sipApplicationDispatcher 7 }

gatherStatistics OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { sipApplicationDispatcher 8 }

requestsProcessed OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipApplicationDispatcher 9 }

responsesProcessed OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipApplicationDispatcher 10 }

congestionControlCheckingInterval OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { sipApplicationDispatcher 11 }

numberOfClientTransactions OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { mobicentsSipServlets 1 }

numberOfServerTransactions OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { mobicentsSipServlets 2 }

numberOfDialogs OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { mobicentsSipServlets 3 }

localMode OBJECT-TYPE
    SYNTAX OCTET STRING (SIZE(0..255))
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { mobicentsSipServlets 4 }

managerTable OBJECT-TYPE
    SYNTAX    SEQUENCE OF ManagerEntry
    MAX-ACCESS    not-accessible
    STATUS    current
    DESCRIPTION
        ""
::= { sipManagerTableDef 10 }

managerEntry OBJECT-TYPE
    SYNTAX    ManagerEntry
    MAX-ACCESS    not-accessible
    STATUS    current
    DESCRIPTION
        ""

        INDEX    {
        IMPLIED managerObjectName
        }
::= { managerTable 1 }

ManagerEntry ::= SEQUENCE {
    managerObjectName    DisplayString,
    managerDistributable    INTEGER,
    managerSessionCounter    INTEGER,
    managerActiveSessions    INTEGER,
    managerMaxActiveSessions    INTEGER,
    managerSessionAverageAliveTime    INTEGER,
    managerExpiredSessions    INTEGER,
    managerRejectedSessions    INTEGER,
    managerMaxInactiveInterval    INTEGER,
    managerSessionMaxAliveTime    INTEGER
}

managerObjectName OBJECT-TYPE
    SYNTAX DisplayString
    ACCESS not-accessible
    STATUS current
    DESCRIPTION
        ""
::= { managerEntry 1 }

managerDistributable OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { managerEntry 2 }

managerSessionCounter OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { managerEntry 3 }

managerActiveSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { managerEntry 4 }

managerMaxActiveSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { managerEntry 5 }

managerSessionAverageAliveTime OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { managerEntry 6 }

managerExpiredSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { managerEntry 7 }

managerRejectedSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { managerEntry 8 }

managerMaxInactiveInterval OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { managerEntry 9 }

managerSessionMaxAliveTime OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { managerEntry 10 }


sipManagerTable OBJECT-TYPE
    SYNTAX    SEQUENCE OF SipManagerEntry
    MAX-ACCESS    not-accessible
    STATUS    current
    DESCRIPTION
        ""
::= { sipManagerTableDef 11 }

sipManagerEntry OBJECT-TYPE
    SYNTAX    SipManagerEntry
    MAX-ACCESS    not-accessible
    STATUS    current
    DESCRIPTION
        ""

        INDEX    {
        IMPLIED sipManagerObjectName
        }
::= { sipManagerTable 1 }

SipManagerEntry ::= SEQUENCE {
    sipManagerObjectName    DisplayString,
    sipManagerDistributable    INTEGER,
    sipManagerSessionCounter    INTEGER,
    sipManagerActiveSessions    INTEGER,
    sipManagerMaxActiveSessions    INTEGER,
    sipManagerSessionAverageAliveTime    INTEGER,
    sipManagerExpiredSessions    INTEGER,
    sipManagerRejectedSessions    INTEGER,
    sipManagerMaxInactiveInterval    INTEGER,
    sipManagerSessionMaxAliveTime    INTEGER,
    sipManagerSipSessionCounter    INTEGER,
    sipManagerSipApplicationSessionCounter    INTEGER,
    sipManagerActiveSipSessions    INTEGER,
    sipManagerActiveSipApplicationSessions    INTEGER,
    sipManagerExpiredSipSessions    INTEGER,
    sipManagerExpiredSipApplicationSessions    INTEGER,
    sipManagerRejectedSipSessions    INTEGER,
    sipManagerRejectedSipApplicationSessions    INTEGER,
    sipManagerMaxActiveSipSessions    INTEGER,
    sipManagerMaxActiveSipApplicationSessions    INTEGER,
    sipManagerSipSessionAverageAliveTime    INTEGER,
    sipManagerSipApplicationSessionAverageAliveTime    INTEGER,
    sipManagerSipSessionMaxAliveTime    INTEGER,
    sipManagerSipApplicationSessionMaxAliveTime    INTEGER,
    sipManagerNumberOfSipSessionCreationPerSecond    INTEGER,
    sipManagerNumberOfSipApplicationSessionCreationPerSecond    INTEGER
}

sipManagerObjectName OBJECT-TYPE
    SYNTAX DisplayString
    ACCESS not-accessible
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 1 }

sipManagerDistributable OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 2 }

sipManagerSessionCounter OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 3 }

sipManagerActiveSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 4 }

sipManagerMaxActiveSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 5 }

sipManagerSessionAverageAliveTime OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 6 }

sipManagerExpiredSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 7 }

sipManagerRejectedSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 8 }

sipManagerMaxInactiveInterval OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 9 }

sipManagerSessionMaxAliveTime OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 10 }

sipManagerSipSessionCounter OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 11 }

sipManagerSipApplicationSessionCounter OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 12 }

sipManagerActiveSipSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 13 }

sipManagerActiveSipApplicationSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 14 }

sipManagerExpiredSipSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 15 }

sipManagerExpiredSipApplicationSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 16 }

sipManagerRejectedSipSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 17 }

sipManagerRejectedSipApplicationSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 18 }

sipManagerMaxActiveSipSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 19 }

sipManagerMaxActiveSipApplicationSessions OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-write
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 20 }

sipManagerSipSessionAverageAliveTime OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 21 }

sipManagerSipApplicationSessionAverageAliveTime OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 22 }

sipManagerSipSessionMaxAliveTime OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 23 }

sipManagerSipApplicationSessionMaxAliveTime OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 24 }

sipManagerNumberOfSipSessionCreationPerSecond OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 25 }

sipManagerNumberOfSipApplicationSessionCreationPerSecond OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS current
    DESCRIPTION
        ""
::= { sipManagerEntry 26 }


END
JBoss.org Content Archive (Read Only), exported from JBoss Community Documentation Editor at 2020-03-11 11:41:59 UTC, last content change 2013-08-30 12:02:53 UTC.